Skip to content

multi: Add label to PublishTransaction #1411

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Apr 29, 2025
Merged

multi: Add label to PublishTransaction #1411

merged 1 commit into from
Apr 29, 2025

Conversation

gijswijs
Copy link
Contributor

This PR chanegs the label used for Txs published to the network. Before, all Txs got the label tapd-asset-minting. Now, the label depends on the context. Currently we use two labels:

  • tapd-asset-minting
  • tapd-asset-send

In the future we could even allow for more granular information being passed to the label.

Copy link
Contributor

@ffranr ffranr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

IMO, we should use

tapd-asset-transfer
tapd-asset-issuance

to align with our proof type terminology.

And maybe even?

TAP-transfer
TAP-issuance

@guggero
Copy link
Member

guggero commented Feb 25, 2025

I vote for:

tapd-asset-transfer
tapd-asset-issuance

@coveralls
Copy link

coveralls commented Feb 25, 2025

Pull Request Test Coverage Report for Build 14731819540

Details

  • 4 of 7 (57.14%) changed or added relevant lines in 5 files are covered.
  • 54 unchanged lines in 8 files lost coverage.
  • Overall coverage decreased (-0.04%) to 28.681%

Changes Missing Coverage Covered Lines Changed/Added Lines %
chain_bridge.go 0 1 0.0%
itest/utils.go 0 1 0.0%
tapfreighter/chain_porter.go 0 1 0.0%
Files with Coverage Reduction New Missed Lines %
address/address.go 2 67.47%
tappsbt/create.go 2 26.74%
rfqmsg/records.go 3 64.11%
tapgarden/caretaker.go 3 68.59%
tapchannel/aux_leaf_signer.go 5 43.08%
tapdb/multiverse.go 6 53.03%
asset/mock.go 8 63.84%
asset/asset.go 25 47.67%
Totals Coverage Status
Change from base Build 14713241690: -0.04%
Covered Lines: 26702
Relevant Lines: 93101

💛 - Coveralls

@Roasbeef
Copy link
Member

Can we go with one of the above ideas so we can merge this?

@lightninglabs-deploy
Copy link

@gijswijs, remember to re-request review from reviewers when ready

@ffranr ffranr force-pushed the publish-tx-label branch from 822bf44 to c19e61d Compare April 29, 2025 12:57
@ffranr
Copy link
Contributor

ffranr commented Apr 29, 2025

Can we go with one of the above ideas so we can merge this?

I've gone with:

tapd-asset-transfer
tapd-asset-issuance

I've also made the labels constants and rebased.

@ffranr ffranr requested review from Roasbeef and guggero April 29, 2025 12:58
Copy link
Member

@Roasbeef Roasbeef left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM 🦺

@github-project-automation github-project-automation bot moved this from 🏗 In progress to 👀 In review in Taproot-Assets Project Board Apr 29, 2025
@Roasbeef Roasbeef merged commit 64ded43 into main Apr 29, 2025
18 checks passed
@ffranr ffranr added this pull request to the merge queue Apr 29, 2025
@github-project-automation github-project-automation bot moved this from 👀 In review to ✅ Done in Taproot-Assets Project Board Apr 29, 2025
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to it being already merged Apr 29, 2025
@guggero guggero deleted the publish-tx-label branch April 29, 2025 19:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: ✅ Done
Development

Successfully merging this pull request may close these issues.

6 participants